Repository navigation
docs(pypi): plan pure-Python packages on GCCcore as EESSI does - #48
Merged
Merged
Conversation
The PyPI how-to inspected and planned beautifulsoup4 on foss/2026.1, and the package-plan skill did the same. EESSI 2026.06 installs Python, Python-bundle-PyPI and BeautifulSoup on GCCcore-15.2.0. A module built on foss/2026.1 loads foss, and with it OpenMPI and FlexiBLAS, for a package that uses neither. The fixture robot could not show the right toolchain either: its files were named GCCcore-14.2.0 but declared foss/2026.1, so a plan at GCCcore/15.2.0 found no Python. The fixture robot now holds Python 3.14.2 and Python-bundle-PyPI 2026.04 on GCCcore-15.2.0, as EESSI 2026.06 does. Its bundle still provides soupsieve, standing in for the real tree, where BeautifulSoup carries it. examples/stacks/eessi-python-gcccore.toml is the matching policy, since a stack policy's toolchain must be the plan's. The page says which to pick: numpy comes from SciPy-bundle, which EESSI installs on gfbf/2026.1, so the numpy example stays on foss/2026.1 with eessi-python-extras.toml. foreign_plan_howtos_use_the_fixture_robots runs the bs4 plan at GCCcore/15.2.0 and checks that the page and the skill show that command and the recipe's dependencies. It fails without the fixture change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PyPI how-to and the
package-planskill plan the pure-Python beautifulsoup4 example onGCCcore/15.2.0, with a GCCcore policy and a real GCCcore-15.2.0 fixture robot.foss/2026.1. EESSI 2026.06 installs Python,Python-bundle-PyPIandBeautifulSouponGCCcore-15.2.0. A module built onfoss/2026.1loads foss, and with it OpenMPI and FlexiBLAS, for a package that uses neither. The fixture robot's files were namedGCCcore-14.2.0but declaredfoss/2026.1, so a plan atGCCcore/15.2.0found no Python.Python-bundle-PyPI2026.04 onGCCcore-15.2.0.examples/stacks/eessi-python-gcccore.tomlis the matching policy. The numpy example stays onfoss/2026.1, becauseSciPy-bundleis never on GCCcore.foreign_plan_howtos_use_the_fixture_robotsruns the bs4 plan atGCCcore/15.2.0and checks that the page and the skill show that command. The commit has a towncrier fragment. Main has no towncrier yet; #26 (fix/towncrier) adds it.